se.cs.ieu.edu.tr
Course Name | |
Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
---|---|---|---|---|---|
Spring |
Prerequisites |
| ||||||||
Course Language | |||||||||
Course Type | Required | ||||||||
Course Level | - | ||||||||
Mode of Delivery | - | ||||||||
Teaching Methods and Techniques of the Course | |||||||||
Course Coordinator | |||||||||
Course Lecturer(s) | |||||||||
Assistant(s) |
Course Objectives | |
Learning Outcomes | The students who succeeded in this course;
|
Course Description |
| Core Courses | |
Major Area Courses | X | |
Supportive Courses | ||
Media and Managment Skills Courses | ||
Transferable Skill Courses |
Week | Subjects | Required Materials |
1 | Introduction | Software Engineering Sommerville – Ch1 |
2 | Concepts of Verification & Validation | Software Engineering Sommerville – Ch22 |
3 | Software testing (concepts of system & component testing) | Software Engineering Sommerville – Ch23/1 |
4 | Software testing (concepts of test case design and automation) | Software Engineering Sommerville – Ch23/2 |
5 | Critical systems validation | Software Engineering Sommerville – Ch24 |
6 | Software cost estimation I | Software Engineering Sommerville – Ch26/1 |
7 | Software cost estimation II (practice) | Software Engineering Sommerville – Ch26/2 |
8 | Midterm | |
9 | Review Practice | Software Engineering Sommerville – Ch22Ch26 |
10 | Quality management I | Software Engineering Sommerville – Ch27/1 |
11 | Quality management II | Software Engineering Sommerville – Ch27/2 |
12 | Product metrics | Software Engineering Pressman – Ch1516 |
13 | Process improvement | Software Engineering Sommerville – Ch28 |
14 | Configuration management | Software Engineering Sommerville – Ch29 |
15 | Review | Lecure Notes |
16 | Review of the Semester |
Course Notes/Textbooks | Software Engineering 8, Ian Sommerville, 8th Ed. Addison Wesley, 2007,ISBN 0321313798Practical Software Testing, Ilene Burnstein, Springer, 2003ISBN 0387951318Software Engineering APractitioners’s Approach, Roger S. Pressman, McGrawHillPublishing Co.; 7th Ed edition (2009), ISBN: 9780071267823 |
Suggested Readings/Materials | Foundations of Software Testing, Aditya P. Mathur, Pearson Education, 2009,ISBN 9788131716601 |
Semester Activities | Number | Weigthing |
Participation | ||
Laboratory / Application | ||
Field Work | ||
Quizzes / Studio Critiques | 3 | 15 |
Portfolio | ||
Homework / Assignments | 2 | 10 |
Presentation / Jury | ||
Project | 1 | 20 |
Seminar / Workshop | ||
Oral Exam | ||
Midterm | ||
Final Exam | 1 | 55 |
Total |
Weighting of Semester Activities on the Final Grade | 6 | 45 |
Weighting of End-of-Semester Activities on the Final Grade | 1 | 55 |
Total |
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Course Hours (Including exam week: 16 x total hours) | 16 | 2 | 32 |
Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | ||
Study Hours Out of Class | 16 | 5 | |
Field Work | |||
Quizzes / Studio Critiques | |||
Portfolio | |||
Homework / Assignments | 2 | 5 | |
Presentation / Jury | |||
Project | 1 | ||
Seminar / Workshop | |||
Oral Exam | |||
Midterms | 1 | 16 | |
Final Exams | 1 | 16 | |
Total | 154 |
# | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | X | ||||
2 | Be able to design and analyze software at component, subsystem, and software architecture level | X | ||||
3 | Be able to develop software by coding, verifying, doing unit testing and debugging | X | ||||
4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | X | ||||
5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | X | ||||
6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | X | ||||
7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | X | ||||
8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | X | ||||
9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | X | ||||
10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | X | ||||
11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | X | ||||
13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest